Brings the example closer to the official `start-basic` shape from
TanStack Router so it reads as an idiomatic Start app rather than a
bespoke harness:

- Drop `@tanstack/router-plugin` dep — covered by `tanstackStart` plugin
- Move port config from `--port` CLI flags into `vite.config.ts`
- Pass `srcDirectory: 'src'` to `tanstackStart` (matches official)
- Simplify build script to `vite build && tsc -p tsconfig.typecheck.json`
- Keep `tsr generate` only in standalone `check-types` (still required
  for the monorepo's turbo-driven typecheck path)

Also strips planning-doc references from test names, comments, and route
copy so the harness reads on its own merits. Renames
`ssr-hypothesis.spec.ts` → `virtualizer-ssr.spec.ts` for the same reason.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Adds a CI workflow that runs on every PR and on pushes to main:

- `lint` — oxlint
- `check-types` — turbo-driven tsc across workspaces
- `test` — vitest unit suite in `package/`
- `e2e` — playwright suite against the tanstack-start example,
  with Playwright browser caching keyed by `pnpm-lock.yaml`

E2E uploads the playwright-report as an artifact on every run for
post-mortem analysis. Concurrency is grouped by ref so PR pushes
cancel in-flight runs while main commits do not.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Vite 7 resolves SSR builds with a separate condition list that does not
inherit from `resolve.conditions` by default. Anywhere we rely on the
workspace `customConditions` to read sibling packages from source, the
SSR resolver must be configured the same way or it falls back to
`import` and demands a built `dist/`.

Updates two configs that prerender or run on the server:

- `docs/vocs.config.ts`: dev-mode-only mirror of the existing client
  conditions, matching vocs's existing dev/prod split (prod still uses
  the published `dist/` of workspace packages, as before).
- `examples/tanstack-start/vite.config.ts`: always-on, both client and
  ssr resolve from source. The example exists to validate SSR layout
  patterns; testing the lib's published shape is a separate concern
  covered by the package's own build pipeline.

`demo` (SPA, no SSR) and `package`'s vitest config (no SSR) need no
change.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>